Auto-detect git remote name instead of assuming 'origin' #2345
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds automatic detection of git remote name when
BASH_IT_REMOTEis not set, fixing issues for users with non-standard remote names likeme,upstream,fork, etc.Problem
Commands like
bash-it version,bash-it update, andbash-it doctorhard-coded the remote name as "origin", causing failures when users have different remote naming conventions:$ bash-it version error: No such remote 'origin'Solution
Created
_bash-it-get-remote-name()helper function that:BASH_IT_REMOTEif already set (preserves user override)git remote | head -n 1Updated three functions to use auto-detection:
_bash-it-update-()(lib/helpers.bash:254)_bash-it-version()(lib/helpers.bash:370)_bash-it-doctor-summary()(lib/helpers.bash:564)Benefits
BASH_IT_REMOTEoverride still worksTesting
BASH_IT_REMOTEenvironment variable preservationFixes #2317
🤖 Generated with Claude Code